5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
- Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-6: Customizing Your Application

The CALL Statement


The CALL statement allows you to invoke non-APPX subroutines when you want to pass and share information between APPX and a subroutine. For example, you could call a special calculator function written in assembly language that is available on your computer system. You pass the appropriate field values to the called routine, and receive back the result of the calculation (by passing the result field with Share? specified as 'Y'for 'yes').

On some computer systems, unique identification of a subroutine name may require more than the 22 characters allowed in the CALL statement. To accommodate this situation, you can define an alphanumeric work field in the data dictionary and set its value to the complete program name. Then, when you specify the CALL statement, you enter the work field name as the program to be called. This approach also minimizes future maintenance by reducing the number of changes you need to make if a revision to the name is required.

There is an indicator that you set when you specify the CALL statement to indicate whether the called routine is to remain resident in memory after it completes execution, so that it can be re-executed by a subsequent CALL without having to read it from disk a second time.

Application Design Manual                                         "Powered by Appx Software"

88

©2006 By APPX Software, Inc. All Rights Reserved